Discover gists

## how-to-setup-plex-with-sonarr-radarr-jackett-overseerr-and-qbittorrent-using-docker.md

      
              1 file
            
          
              0 forks
            
          
                0 comments
              
            
              2 stars
            
          
                duraki
                / how-to-setup-plex-with-sonarr-radarr-jackett-overseerr-and-qbittorrent-using-docker.md
            
            
              Created
              July 25, 2025 02:03
                — forked from rickklaasboer/how-to-setup-plex-with-sonarr-radarr-jackett-overseerr-and-qbittorrent-using-docker.md
            
              
                How to setup Plex with Sonarr, Radarr, Jackett, Overseerr and qBitTorrent using Docker
              
          
    How to setup Plex with Sonarr, Radarr, Jackett, Overseerr and qBitTorrent using Docker

Before continuing: This guide is currently outdated but I'm working on a new one with upgrading steps included. I'll link it here once it's finished :)
This is a guide that will show you how to setup Plex Media Server with Sonarr, Radarr, Jackett, Overseerr and qBitTorrent with Docker. It is written for Ubuntu 20.04 but should work on other Linux distributions as well (considering supported distributions by Docker). It is also written for people who have some experience with Linux and Docker. If you are new to Docker, I recommend you to read the Docker documentation, and if you are new to Linux, I recommend you to read the Ubuntu documentation.
Now, let's get started!
Please note: This guide was written without considering hardlinking for Sonarr/Radarr. If you want to use hardlinking refer to #Hardlinking

  
## javascript_engines_and_runtimes.md

      
              1 file
            
          
              15 forks
            
          
                13 comments
              
            
              180 stars
            
          
                guest271314
                / javascript_engines_and_runtimes.md
            
            
              Last active
              April 20, 2026 08:17
            
              
                A list of JavaScript engines, runtimes, interpreters
              
          
V8


V8 is Google’s open source high-performance JavaScript and WebAssembly engine, written in C++. It is used in Chrome and in Node.js, among others. It implements ECMAScript and WebAssembly, and runs on Windows 7 or later, macOS 10.12+, and Linux systems that use x64, IA-32, ARM, or MIPS processors. V8 can run standalone, or can be embedded into any C++ application.


SpiderMonkey


SpiderMonkey is Mozilla’s JavaScript and WebAssembly Engine, used in Firefox, Servo and various other projects. It is written in C++, Rust and JavaScript. You can embed it into C++ and Rust projects, and it can be run as a stand-alone shell. It can also be [compiled](https://bytecodealliance.org/articles/making-javascript-run-fast-on


## termcap.bash
# annotated by dave eddy (@yousuckatprogramming)
# explained - https://youtu.be/D0sG2fj0G4Y
# borrowed heavily from https://grml.org

# Begin blinking text mode
# I just use bold red here since my terminal has blinking disabled
export LESS_TERMCAP_mb=$'\e[1;31m'

# Begin bold text mode
export LESS_TERMCAP_md=$'\e[1;31m'

## llm-wiki.md

      
              1 file
            
          
              4722 forks
            
          
                615 comments
              
            
              22040 stars
            
          
                karpathy
                / llm-wiki.md
            
            
              Created
              April 4, 2026 16:25
            
              
                llm-wiki
              
          
    LLM Wiki

A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
The core idea

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.

  
## MultiSimConverter.cs
///
/// This code is licensed under the terms of the MIT license
///

using System.Runtime.CompilerServices;
using System.Runtime.InteropServices;
using System.Text;
using System.Text.RegularExpressions;

namespace MultiSimConverter

## zodiac.cpp
#include <windows.h>
#include <winhttp.h>
#include <iostream>
#include <string>

#pragma comment(lib, "winhttp.lib")

using namespace std;

wstring GetHoroscope(const wstring& sign) {
	# annotated by dave eddy (@yousuckatprogramming)
	# explained - https://youtu.be/D0sG2fj0G4Y
	# borrowed heavily from https://grml.org

	# Begin blinking text mode
	# I just use bold red here since my terminal has blinking disabled
	export LESS_TERMCAP_mb=$'\e[1;31m'

	# Begin bold text mode
	export LESS_TERMCAP_md=$'\e[1;31m'
	///
	/// This code is licensed under the terms of the MIT license
	///

	using System.Runtime.CompilerServices;
	using System.Runtime.InteropServices;
	using System.Text;
	using System.Text.RegularExpressions;

	namespace MultiSimConverter
	#include <windows.h>
	#include <winhttp.h>
	#include <iostream>
	#include <string>

	#pragma comment(lib, "winhttp.lib")

	using namespace std;

	wstring GetHoroscope(const wstring& sign) {